-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[infra] hosts table metrics #173708
[infra] hosts table metrics #173708
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
/ci |
/ci |
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
Hi @klacabane Great work, good to see the new performance journey 🔥 Code LGTM and thanks for adding monitoring chart, I added it to the dashboard and will setup alerting to make sure we got notified whenever journey metrics are changing. Hope you don't mind a small addition I pushed in 066ae0b In the past with the help of perf journey we spotted that suggestion charts in Lens Editor have inconsistent rendering time (and customers were reporting it too), so I think it might it useful to track it. |
Hi @dmlemeshko, thanks for the change makes sense to already have the journey baseline include charts. Adding charts load time is planned, do you know if there are any examples of that ? |
You can use Lens Editor EBT instrumentation #163089 as example. I had a quick look and there are few ways to do it: report duration for each LensWrapper + Metric Chart Wrapper individually (I'm sure I put the startTime incorrectly, but just as an example) and end up with 5 separate events or somehow handle loading state completion for the whole KPIGrid (1 event, optionally with details for each lens metric). Each team has its own preference regarding events structure and level of details, we only suggest split it into time-to-data & time-to-render to better understand the trends (e.g. slow trend is in data fetching, rendering time remains consistent) |
This reverts commit 2344594.
@elastic/obs-ux-logs-team @elastic/obs-ux-infra_services-team still looking for review :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀 I tried it locally, thank you for adding that!
await kibanaPage.waitForCharts({ count: 5, timeout: 60000 }); | ||
}); | ||
|
||
export function generateHostsData({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice 🤩 I am happy to see that we can use synthrace for host test data generation 💯
packages/kbn-apm-synthtrace/src/lib/infra/infra_synthtrace_kibana_client.ts
Outdated
Show resolved
Hide resolved
telemetry.reportPerformanceMetricEvent( | ||
'infra_hosts_table_load', | ||
duration, | ||
{ key1: 'data_load', value1: duration }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now we only record the data loading duration, I've set it as key1
if we want to extend the event with more metrics (ie render time) but atm using either duration
or value1
is similar.
Looking at metrics again I can't find the actual duration of the journey, we get different events associated with the journey (getAllTag
, kibana_loaded
..) but I'm not sure if one of these actually represents the journey execution time @dmlemeshko do you know how we can get the journey duration ?
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Summary
Closes #172475
system
package and can produce all datasets queried by host viewTesting
PERFORMANCE_ENABLE_TELEMETRY=1 node scripts/run_performance.js -v --journey-path x-pack/performance/journeys/infra_hosts_view.ts